Systems and Methods of Database Optimization and Distributed Computing

ABSTRACT

Systems and methods of database optimization and distributed computing are provided herein. In some embodiments, a method includes distributing remote agents to a plurality of remote computing systems, receiving incoming inventory from a database of available inventory via the remote agents, generating standardized inventory records, generating the database of available inventory that retains complete standardized inventory records, generating thin locator style records for the complete standardized inventory records, wherein the thin locator style records include key record identifiers, receiving a query, generating a standardized query, selecting the thin locator style records in response to the standardized query, obtaining the complete standardized inventory records corresponding to the thin locator style records of the selected key record identifiers, and providing the complete standardized inventory records to a requestor.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation-in-part of U.S. application Ser. No.15/639,599, filed Jun. 30, 2017, which is a continuation-in-part of U.S.application Ser. No. 13/719,130, filed Dec. 18, 2012, which is acontinuation of U.S. application Ser. No. 13/228,407, filed Sep. 8,2011, now U.S. Pat. No. 8,370,215, which is a continuation of U.S.application Ser. No. 12/883,154, filed Sep. 15, 2010, now U.S. Pat. No.8,036,952, which is a continuation of U.S. application Ser. No.12/705,328, filed Feb. 12, 2010, which is a continuation-in-part of U.S.application Ser. No. 12/475,368 filed May 29, 2009, which is acontinuation-in-part of U.S. application Ser. No. 12/215,940, filed Jun.30, 2008, which claims the benefit of U.S. Provisional Application No.60/937,856, filed Jun. 30, 2007, the disclosures of which are allincorporated herein by reference in their entirety including allreferences cited therein.

BACKGROUND OF THE INVENTION Field of the Invention

The present disclosure relates generally to database optimization anddistributed computing. In some embodiments the system and methods of thepresent disclosure are directed to distributed computing agents thatprovide efficient database maintenance through generation of thinlocator style records for full database records and use of these thinlocator style records for database updates and execution of queries forfull database records. The disclosure further discloses the updating ofdatabase records in a standardized record format and quote requestswhere the database queries use terms matching the standardized databaserecord format for the fields.

SUMMARY OF THE INVENTION

Example methods and systems comprise: distributing remote agents to aplurality of remote computing systems, receiving incoming inventory fromthe database of available inventory via the remote agents, generating adatabase of available inventory that comprises complete inventoryrecords, generating thin locator style records for the completeinventory records, wherein the thin locator style records comprise keyrecord identifiers, selecting thin locator style records in response tothe standardized query, obtaining complete standardized inventoryrecords corresponding to the thin locator style records of the selectedkey record identifiers, and providing the complete standardizedinventory records to a requestor.

Embodiments of the present disclosure comprise a system having: remoteagents distributed to a plurality of remote computing systems; and aserver in communication with the remote agents that: (i) receivesincoming inventory from the database of available inventory from theremote agents; (ii) generates a standardized inventory record; (iii)generates a database of available inventory that comprises completestandardized inventory records; (iv) generates thin locator stylerecords for the complete standardized inventory records, wherein thethin locator style records comprise key record identifiers; (v) receivesa query and generates a standardized query, (vi) selects thin locatorstyle records in response to the standardized query; (vii) obtainscomplete standardized inventory records corresponding to the thinlocator style records of the selected key record identifiers; and (viii)provides the complete standardized inventory records to a requestor.

Further embodiments of the present invention may further includecomputer-readable storage media having embodied thereon programsexecutable by a processor to perform a method for automated alternativesselection for compound price quotes. Such computer-readable storagemedia may provide for performance via integration into existing clientsystems and/or via plug-in.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1A illustrates an exemplary architecture for generating a pricequote.

FIG. 1B illustrates an alternative architecture for generating a pricequote according to another embodiment of the present invention.

FIG. 2 illustrates an exemplary embodiment of a quoting engine systemfor generating a price quote.

FIG. 3 illustrates an exemplary architecture for receiving dealerinformation.

FIG. 4 illustrates an exemplary method for alternative selection forcompound price quotes.

FIG. 5A illustrates an exemplary screenshot of a compound price quoteaccording to one embodiment.

FIG. 5B illustrates an exemplary screenshot of a compound price quoteaccording to an alternative embodiment.

FIG. 5C illustrates an exemplary screenshot of a compound price quoteaccording to another alternative embodiment.

FIG. 6 is a schematic diagram of another example system of the presentdisclosure.

FIG. 7 is a flow diagram of an improved database management methodthrough the system of FIG. 6.

FIG. 8 is a schematic diagram of another example system of the presentdisclosure that provides improved database management.

FIG. 9 is a flowchart of an example method of the present disclosurethat illustrates distributed agent computing and database queryoptimization.

FIGS. 10A-G collectively illustrate a flow process of inventorymanagement that includes the flow diagram of FIGS. 7.

DETAILED DESCRIPTION

The accompanying drawings, where like reference numerals refer toidentical or functionally similar elements throughout the separateviews, together with the detailed description below, are incorporated inand form part of the specification, and serve to further illustrateembodiments of concepts that include the claimed disclosure, and explainvarious principles and advantages of those embodiments.

The methods and systems disclosed herein have been represented whereappropriate by conventional symbols in the drawings, showing only thosespecific details that are pertinent to understanding the embodiments ofthe present disclosure so as not to obscure the disclosure with detailsthat will be readily apparent to those of ordinary skill in the arthaving the benefit of the description herein.

When making purchases, one of the most important considerations for abuyer is price. However, pricing can be dependent on multiple factors:including type of item, specifications and features of the item, age,mileage, demand, degree of use (i.e., used, new), location,seller/dealer, etc. Such factors may affect the price dramatically andfurther complicate the process of determining, analyzing, and comparingprices for a desired product. Automobiles, for example, may come invarious makes, models, trims, colors, features (standard equipment,options, and upgrades), etc. Such options and upgrades, or removalthereof, may increase or decrease the price of the final product.

Another consideration when customers are shopping for a particularproduct is availability, specifically availability within a certaingeographic region. Many customers wish to see, touch, and test a productbefore committing to a purchase, especially costly purchases. Somevehicles, due to size, weight, rarity, etc., may be difficult, costly,or time-consuming to transport to the customer. As such, the customermay wish to find a seller or dealer of the product within a certaingeographic region that is convenient to the customer. The geographiclocation of a car dealer, for example, may be an important factor to acar-buyer, since transporting an automobile from a distant location maybe either costly, time-consuming, or both. Determining availabilitywithin a geographic region therefore becomes very important to thecustomer.

In some instances, a customer may request a particular vehicle, but maybe open to considering alternatives, particularly if the alternative hasa more attractive price point or has a different set of desirablefeatures. Such alternatives may include vehicles that share somesimilarities to the requested vehicle, but may not turn up in a searchfor the requested vehicle. For example, a customer who requests aparticular make and model of truck may be open to purchasing alternativetrucks, either of the same make, model, year, trim, color, body style,usage level, etc. Because customers generally lack the ability to reviewdealer inventories, however, they may not know to ask whether suchalternatives exist or are available.

As such, there is therefore a need in the art for improved systems andmethods for selection of alternatives and generation of compound pricequotes, including quotes for alternatives.

Embodiments of the present invention include methods and systems foralternatives selection for compound price quotes. A database ismaintained regarding a variety of vehicles and the features associatedwith each. A requesting party submits a request that includesinformation regarding at least one specification. Search results areretrieved from the database regarding the specification provided by therequest. It is determined that the search results do not meet apredefined target, and an alternative specification is identified. Atleast one other set of search results is retrieved from the database.Vehicles are selected from the first set or subsequent sets of searchresults in order to meet the target. A price quotes is generated foreach of the selected vehicles. The automated nature of such price quotesprovides a customer with information that is timely, detailed, andaccurate with respect to features, pricing, and availability. Inaddition, identifying alternatives and providing quotes for suchalternatives provides the requesting party with choice and variety. Suchprice quoting also provides dealers with speed of response to therequesting party, more pricing flexibility, greater accuracy, andsignificant time savings.

FIG. 1A illustrates an exemplary architecture for generating anautomated price quote. The parties involved may include the customer110, dealer (or seller) 120 of a product, and the quoting engine 200. Inthe illustrated embodiment, the customer 110 communicates with quotingengine 200, which in turn, can convey information to the dealer 120through the dealer's customer relationship management (CRM)/Internetlead management (ILM) system.

FIG. 1B illustrates an alternative architecture for generating a pricequote according to another embodiment of the present invention. Such anarchitecture may result from a plug-in model, in which price quoting inintegrated into the CRM/ILM system of the dealer. As such, the customercommunicates with the dealer's 120 CRM/ILM system, the CRM/ILM systemcommunicates the issuance of the price quote to the quoting engine 200,the quoting engine 200 issues the price quote to consumer 110.

Searching the database 210 can be more efficient if consistent terms areused and thus a search is for an exact match. However, the inventoryrecords received from dealers or other suppliers may use identifiablebut different terms. Different dealership records may refer to the cartype using different or abbreviated terms. Thus, the fields in adatabase query request can be identified and transformed into a databasecompatible format. For example, a dealership inventory record or quoterequest may refer to the car type as a CHEV where the database usesCHEVROLET. Other examples of how queries or inventory record updates canvary from the database format include using “DL” where the database 210may use “Deluxe”, “SDN” instead of “Sedan”, “19” instead of the fullyear “2019”. Thus, in one embodiment, to access the database 210 or tostore a new inventory record, the remote agent inventory record ischange into a standardized inventory record by mapping fields in therecord to a standardized field value. Additionally, a dealer or customerrequest for a price quote can be transformed into standardized fieldsterms.

The quote request, provided by the dealership, can be formatted as astring which can be parsed into tokens. The tokens can be identified tobelong to a particular field in the database. Example fields include butare not limited to make, model, year, trim, color, body style, vehiclesegment, duty type, option, use level, inventory age, equipment level,and vehicle identification number (VIN). For example, '19 or 19 could bemapped to 2019. SND, 4-door, 4 door, and any other abbreviation of“Sedan” can be mapped to a standard format query or into a standardformat inventor record.

FIG. 2 illustrates an exemplary embodiment of a quoting engine system200 for generating a price quote. The quoting engine 200 includes adatabase 210, a matching engine 220, and a price quote preparationengine 230. Database 210 stores information concerning various productspecifications.

If the product is a vehicle, for example, database 210 may store vehiclemappings 210A, vehicle configurations 210B, vehicle information 210C,information from dealer inventory feeds 210D, dealer pricing rules 210E,manufacturer incentives 210F, and communication templates 210G, asillustrated in FIGS. 2.

Vehicle mappings database 210A includes various translations understoodto be a particular vehicle by the quoting engine 200. For example, acustomer 110 may request a particular vehicle (e.g., 2009 Toyota CorollaLE 4-door sedan), while the quoting engine 200 understands the samevehicle as a 2009 Toyota Corolla LE 4-dr SDN. Because the descriptionsare slightly different, quoting engine 200 may map, translate, orotherwise understand that both descriptions apply to the same vehiclebased on information stored under vehicle mappings database 210A:

2009 Toyota Corolla LE 4-dr SDN=2009 Toyota Corolla LE 4-Door Sedan

The matching is performed by matching engine 220. Once an incoming pricequote request is received from the customer 110, a product descriptionmay be identified in the request and matched to a product description ofone or more dealers 120 by matching engine 220. Matching engine 220 usesthe information stored in vehicle mappings 210A to determine whatproduct is being requested by the customer 110. In some embodiments, newand updated vehicle mappings may be added manually, automatically, orboth, to vehicle mappings database 210A. Some embodiments may trackmanual mappings, determine that manual mappings have occurred a certainnumber of times, and store the particular mappings under mappings 210Afor automatic mapping in the future.

Vehicle configurations database 210B includes information concerningspecific products. Such information may be expressed as any combinationof options or features associated with a vehicle identified by matchingengine 220. The configurations may be stored in the form of a specificvehicle as uniquely identified by its VIN number (very specific) orvehicle configurations available at a given dealership or dealerships ina geographic region (less specific). For a given combination of “Year,Make, Model” or “Year, Make, Model, Trim,” vehicle configurationsdatabase 210B may list multiple vehicle configurations that will beincluded in the price quote. In some embodiments, new and updatedconfigurations may be added to vehicle configurations database 210B dueto the use of the quoting engine 200, just as new mappings may be addedto vehicle mappings 210A.

Vehicle information 210C includes further information and specificationsfor a given vehicle type. The information in 210C provides customer 110of the vehicle price quote with the vehicle's description as well as thedescriptions of the options, features, and equipment available and/orincluded on the quoted vehicles. For example, a customer 110 may requesta particular make and model, but be unaware of what further options andfeatures are available. Such information may be accessed from vehicleinformation 210C of the database 210 and provided to the customer 110,for each vehicle within the compound price quote.

Exemplary specifications may include make, model, year, trim, color,body style, vehicle segment, duty type, option, use level, inventoryage, equipment level, and vehicle identification number (VIN). Make mayrefer to a manufacturer branded line of vehicles (e.g., Ford, Toyota,Nissan). Model may refer to a specific branded model of vehicle withinthe line (e.g., Focus (Ford), Camry (Toyota)). Trim may refer to a styleof vehicle for the model (e.g., DX, EX, LX). Body style may refer to aclassification of vehicles based on a type of vehicle body (e.g., sedan,truck, sport utility vehicle (SUV)) independent of the particularmanufacturer. Vehicle segment may refer to another generalizedclassification of vehicles (e.g., compact, mid-sized, luxury, all-wheeldrive (AWD)). Duty type may refer to any sub-classification within abody style or vehicle segment (e.g., light duty, heavy duty).

In addition, options may include any additional features or accessoriesthat may be included or added to a vehicle (e.g., sound system, securitysystem, global positioning system (GPS)). Use level may refer to whetherthe vehicle is new, pre-owned, and indicators regarding extent of usage,such as mileage. Inventory age may refer to a length of time the dealerhas had the particular vehicle in inventory. Equipment level may referto a generalized classification regarding the various features oroptions included in a vehicle (e.g., conservatively equipped,comfortably equipped, generously equipped). A VIN is a unique identifierassociated with each vehicle. Within a dealership, the vehicle may alsobe referred to by a stock number.

Dealer inventory feed database 210D includes lists of vehicles currentlyat a given dealer 120 along with information that may be obtained bydecoding the vehicle identification number (VIN) number associated witheach vehicle. This database is used to provide information relating toactual new and used vehicles available from a particular dealer 120 thatmay match the price quote request submitted by the customer 110. In someembodiments, available alternatives to the new vehicle may be determinedand presented to the customer 110. Such alternatives may includehigher-end models/trims, lower-end models/trims, as well as used/newalternatives. For example, a customer 110 requesting a price quote for aused vehicle may also be presented with price quotes for new vehicleswith the same (or similar) specifications, and vice versa. Theinformation stored in dealer inventory feed database 210D may bereceived from multiple dealers in any geographic region. FIG. 3,described in further detail below, illustrate one way that informationmay be provided to data inventory feed database 210D.

Dealer pricing rules database 210E includes rules and the pricing valuesby which the dealer 120 arrives at the final price of a given vehicle.These rules are stored in advance of an incoming vehicle price quoterequest.

Manufacturer incentive database 210F contains manufacturer incentivesoffered directly to customer 110. These incentives may include cash backrebates, special financing rates, or special lease rates to influence acustomer's purchase decision.

Communication template database 210G is stored in advance of theissuance of a price quote. The template may contain information layout,copy, graphics or the like that may be used at the time a vehicle pricequote request is issued. The communication method used to inform thecustomer 110 of a vehicle price quote may be e-mail, webpage, textmessage, mobile communication, and other forms of communication commonlyused in the art.

Searching the information available in database 210A-G allows fordetermination of answers to the following questions:

-   -   What is the specified product,    -   Whether the specified product is available in the specified        geographical region and from what dealers,    -   What other specifications are available for the specified        product,    -   How many units of the specified product are available from a        dealer,    -   How much the dealer is quoting for the specified product,    -   Whether any alternatives exist and any cost adjustment for each        alternative,    -   Whether the specified product qualifies for any manufacturer        incentives (e.g., cashback rebates, special financing options,        special lease rates),    -   Which sales representative at a dealership is issuing the price        quote,    -   How the price quote will appear to consumer 110 and the means of        delivery.

FIG. 3 illustrates an exemplary architecture for receiving dealerinformation. The availability of a product by configuration, as well asby dealer 120 or dealers 120 in a geographic region, may need to bedetermined before generation of a price quote. In some cases such as thecustomer 110 calling the dealer 120 by telephone or requesting anupdated/refined price quote based on new information provided to thedealer 120, a dealer 120 may request the issuance of a price quote onbehalf of a customer 110.

The dealer 120 as part of requesting the issuance of a price quote toconsumer 110 may select an existing vehicle configuration from thevehicle configurations database 210B or create a new vehicleconfiguration if needed. Alternatively, the request for issuing a pricequote by dealer 120 may be based on a regional vehicle search using atool such as a regional vehicle locator 310 provided by, for example,the original equipment manufacturer (OEM), prior to submitting the pricequote request. Regional vehicle locator 310 operates in conjunction withinventory supply management (ISM) systems at one or more dealers 120 toprovide dealer cost and inventory availability of a vehicle manufacturedby the OEM. Multiple uses of the regional vehicle locator 310 providesfrequent updates 311-314 (e.g., Price Quote Tool Dealership A, ISM 1,Price Quote Tool Dealership A, ISM 2, Price Quote Tool Dealership B, ISM1, and Price Quote Tool Dealership B, ISM 2, respectively) concerningsuch dealer cost and inventory of one or more dealers 120 in ageographic region. As such, the information concerning inventory ofvehicles available across dealerships within a particular region may becontinuously provided to quoting engine 200. Upon locating a vehicle inthe region, the dealer 120 may submit a price quote request on behalf ofthe customer 110 based on the configuration of the vehicle retrievedfrom the regional vehicle locator 310. As such, the particular vehicleconfiguration is passed along to the quoting engine 200 and stored invehicle configurations database 210B.

FIG. 4 illustrates an exemplary method 400 for alternatives selectionfor compound price quotes. Method 400 may include maintaining a databaseof vehicles and their respective features, receiving a quote requestindicating a specification, retrieving a set of search results from thedatabase based on the specification, determining that the set of searchresults does not meet a target, determining an alternative to thespecification, retrieving a set of search results based on thealternative, selecting a plurality of vehicles in order to meet thetarget, the selections coming from the first set or subsequent sets ofsearch results, and generating a compound price quote including quotesfor a plurality of vehicles in a response to the request.

In step 410, a database is maintained regarding multiple vehicles andthe features associated with each vehicle.

Each vehicle in database 210 may be associated with a dealer/locationand described in terms of its specifications such as make, model, year,trim, color, body style, vehicle segment, duty type, option, use level,inventory age, equipment level, price, and vehicle identification number(VIN). The database may be searched based on a variety of parameters.For example, a search may be based on geographic location such that thevehicles available from one or more dealers in a particular geographiclocation may be identified. The available vehicles may further befiltered based on one or more specifications (e.g., make, model).Changing the specifications allows for different results to beretrieved.

In step 420, a price quote request is received. Such a price quoterequest may be sent directly from a customer 110 or from a dealer 120,who may be submitting the price quote request on behalf of one or morecustomers 110. The price quote request may indicate a particular productof interest and at least one specification indicating a feature. Forexample, a price quote request may be as broad as “Blue Honda Civic” oras specific as indicating an exact vehicle by VIN. The price quoterequest may further specify preferences with respect to any feature ofthe requested vehicle. Such preferences may specify a particular model,trim level, body style, price range, equipment level, presence of aparticular option, etc. Alternatively, the preference may indicate aminimum level of a feature (e.g., at least LX trim), such that higherlevels may be acceptable and of interest to the requesting party. Thepreference may also indicate a maximum level (e.g., no more than$40,000) to allow for lower levels to be retrieved for consideration.

In the step 420, the price quote is converted into a database query.This step can map quote terms to the standardized terms used by thedatabase 200. For example, a quote for a '18 CHEVY can result in a queryfor a CHEVROLET in the database make field and 2018 in the database yearfield.

In step 430, a set of search results is retrieved from database 210based on the specification(s) indicated in the request. As part of thesearch, the specification provided in the price quote request iscompared to the information stored in mappings 210A. For example, aprice quote request concerning a particular make and model isautomatically mapped/translated to the description understood by quotingengine 200. Specifically, availability information regarding one or moredealers in or around a particular location may be determined. If asearch is based on make and model (e.g., Toyota Camry), for example, aset of search results may include information regarding the twentyToyota Camry vehicles available from the local Toyota dealer.

In step 440, it is determined whether the predefined target is met whenincluding alternatives in the compound price quote. The target mayinclude one or more parameters predefined by a dealer, an administrator,the user, or a combination of the foregoing. The target may refer to thetype(s) of search results desired. For example, a target may refer to adesired number of results (e.g., different vehicle configurations,different price quotes), a desired range of results (e.g., price range),etc. Rather than just giving just one quote for one vehicle or oneaverage quote, a dealer may wish to provide its customers with specificprice quotes for multiple vehicles, for example, representing a range ofprices and/or features. Additionally, the dealer may want to includealternative pre-owned vehicles within the compound price quote when therequest is for a new vehicle and vice versa (i.e., including alternativenew vehicles within the compound price quote in response to a requestfor a pre-owned vehicle).

For example, a dealer may specify that its customers receive at leastthree price quotes in low, medium, and high ranges that are at least$2000 apart. A customer of that dealer who searches for a 2010 ToyotaCamry CE may therefore receive price quotes for three 2010 Toyota CamryCE vehicles with price quotes of $25,000, $30,000, and $35,000. Where arequest does not specify trim or the dealer wants to include alternativetrims within the compound price quote, the differences in the pricequotes may be based on differing trim (e.g., DX, LX, EX). The differencein price quotes may further be based on differences in other featuresnot specifically enumerated in the request (e.g., options, duty level,equipment level). If the search results meet the target, then the methodmay proceed to step 480 for price quote generation.

If the search results do not meet the target, the method may proceed tostep 450. Depending on how specific the specifications of the searchare, a dealer may not have any or enough vehicles in inventory that meetthe requested specification. Where search results based solely on arequest fails to meet a target number, close alternatives may beidentified. As such, in step 450, an alternative specification may bedetermined. Selection of the alterative specification may be based ondefault parameters and/or be defined based on preferences of a dealer,administrator, etc. Depending on the target specified, the alternativespecification may be chosen to substitute or supplement the requestedspecification to broaden, narrow, or otherwise supplement the search.

FIG. 5A illustrates an exemplary screenshot of a compound price quoteaccording to one embodiment. Specifically, the illustrated compoundprice quote is based on a price quote request for a specific VIN of a2008 Chevrolet Impala LT. Based on the dealer inventory, a search basedon a particular VIN number may not retrieve any results or onlyretrieves one result, despite the target specifying at least fourresults. To find alternatives to include in the price quote, analternative specification may be substituted, specifying a differentyear, make, model, trim, etc.

An alternative specification may pertain to a feature not specified inthe request, but identified from the retrieved search results. Forexample, a search may refer to a vehicle having a particular VIN.Information regarding that vehicle may be retrieved, and the make,model, and other features of the vehicle having that VIN number may bedetermined. Referring to the previous example, a particular 2008Chevrolet Impala LT may be identified from the VIN number. In selectingalternatives to meet the target, the determined alternativespecification may broaden the search to find vehicles having the same orsimilar vehicle configuration or combination of features. A subsequentsearch may retrieve other Chevrolet Impala LT vehicles (e.g., samemake/model/trim), other Chevrolet Impala vehicles (e.g., samemake/model), other sedans (e.g., same body style), etc., based onalternate and/or broader specifications.

Similarly, where the retrieved vehicle has a particular usage status(e.g., pre-owned), an alternative specification may be a different usagestatus (e.g., new). Requests for a pre-owned vehicle may thereforeresult in quotes for not only the pre-owned vehicles, but also newalternatives matching other features of the requested vehicle. The samelogic may apply to determination of an alternative specification for anyother feature or combination of features specifying make, model, year,trim, color, body style, vehicle segment, duty type, option, use level,inventory age, equipment level, etc.

In step 460, a set of search results is retrieved based on thealternative specification. Referring again to FIG. 5A, a search for aparticular 2008 Chevrolet Impala LT may retrieve that vehicle.Alternatives may include a 2008 Chevrolet Impala LS (e.g., differenttrim), a 2009 Toyota Camry Hybrid sedan, and a 2009 Camry SE sedan((e.g., different make/model, similar body style).

Additionally, FIG. 5B illustrates an exemplary screenshot of a compoundprice quote according to alternative embodiments of the invention. Withrespect to the heavy-duty 2008 Ford Expedition, the alternatives mayinclude additional options within the same year, make, model and trim(e.g., “air suspension read—load leveling” and “rear seat entertainmentDVD”). While it is possible for customer 110 to specify a desiredproduct configuration, the product manufacturer (e.g., OEM) may not havebuilt such a configuration. In such a case, an alternative/equivalentproduct may be selected. For example in the case of the 2008 FordExpedition, the price quote request may have contained the desire for aheavy duty radiator which was not built for Expeditions within thecustomer 110's region. FIG. 5B illustrates the alternatives availablewhich do not include the heavy duty radiator. The particular productconfiguration (or alternative/equivalent) can then be determined basedon a preprogrammed selection algorithm. Preprogramming may be based ondefault configurations and/or customized by dealer 120, OEM , etc.

FIG. 5C illustrates an exemplary screenshot of a compound price quoteaccording to alternative embodiments of the invention. With respect tothe 2009 Honda Civic, the price quote request may be for the LX 5-SpeedAutomatic 4dr Sedan and the alternatives are based on differing trims ofthe same Civic model (i.e., the LX-S and the EX) each of which havevarying levels of equipment, ranging from a “conservatively equipped”unit to a “comfortably equipped unit” to a “generously equipped” unit.

In step 470 for some embodiments of the invention, representativevehicles are selected from the first set of search results based on therequested specification or the second set of search results based on thealternative specification. In some instances, the search incorporatingthe requested specification may retrieve too many vehicles to meet thetarget. As such, representative vehicles may need to be selected tocomply with the target. For example, the search may need to be filteredto meet the target based on an alternative specification. Thealternative specification may therefore supplement the requestedspecification in narrowing down the search results to meet the target.For example, a request for a “2010 Toyota Camry CE sedan” may result in10 matches from a dealer who has defined a target to provide one vehicleeach for a high price range, a middle price range, and a low pricerange. The ranges may be determined by taking the difference between thehighest price (e.g., $40,000) and lowest price (e.g., $31,000) anddividing into thirds (e.g., $40,000-$31,000=$9000; $9000/3=$3000). Thelow range would be $31,000-$34,000; the middle range would be$34,000-$37,000; and the high range would be $37,000-$40,000. A dealermay specify any number of ranges as part of defining their respectivetargets for price quoting.

In this embodiment, the alternative specification may refer to a countof vehicle configurations (e.g., vehicles with the same features)identified for each price range. A vehicle having a configuration withthe highest count within each price range (e.g., 2010 Toyota Camry CEsedans with leather seats, GPS, leather seats and GPS) would be selectedfor inclusion in the price quote. Where there are ties in number ofconfigurations within each price range, additional factors may come intoplay. For example, depending on which range the vehicle configurationfalls into, a vehicle with the cheapest, median, or priciest vehicleconfiguration may be selected. Another factor in the selection iswhether the prices of the selected vehicle configuration representenough of a range for comparison.

Once the vehicles have been selected, the method may return to step 440for determination of whether the target has been met. If so, the methodproceeds to step 480 for generation of each price quote for the selectedvehicles.

In step 480, a compound price quote is generated for the vehiclesretrieved in steps 430 and/or 460. The compound price quote includes aprice quote for each of a plurality of vehicles, each calculatedaccording to the particular pricing scheme of the dealer(s) 120. Apricing scheme is a set of one or more pricing rules for a particularvehicle configuration. The pricing rules specified by a particulardealer 120 may refer to absolute selling price, pricing relative to theproduct's manufacturer-suggested retail price (MSRP), or pricingrelative to the dealer's invoice price. Dealer invoice pricing may beobtained from the dealership in absolute fashion or through a formulaiccalculation. The dealer 120 may also specify different rules fordifferent configurations. As such, multiple pricing schemes may beassociated with a particular dealer 120. For each vehicle, a pricingscheme may be identified from possibly multiple pricing schemes bydealer 120 and determined as being relevant to the specified product andcustomer.

Further, customer incentive information may also be provided bymanufacturer incentives 210F in database 210 and applied to generate theprice quote. This information may include but is not limited to cashback rebates, special financing rates, or special lease rates. In someinstances, special pricing rules may apply. For example, a dealer 120may be having a sale during a particular weekend in which afriends-and-family discount is available. Such special pricing rules mayalso be taken into account in the generation of the price quote.

The identified pricing scheme is applied to determine a price quote foreach vehicle. A response may be prepared including the multiple pricequotes and sent to the requesting party, which may be a customer 110 ora dealer 120. In addition to the price quote, other information may beprovided to assist the customer 110 in making a decision. For example, adetailed description of each vehicle (including various otherspecifications available) may be provided from vehicle information 210Cstored in database 210.

Further, if the dealership wishes to indicate that the compound pricequote has been sent on behalf of a particular individual (i.e., a salesrepresentative), such information may also be sent along with the pricequote. Such information, along with dealer-specific information (i.e.,address, operating hours) may be provided by communication template 210Gstored in database 210. The information for the vehicle price quote isincorporated into the template dynamically to produce the desiredvehicle price quote communication. The compound price quote (and anyaccompanying information) may then be issued via e-mail, web, SMS, text,mobile communication and others known in the art. If the compound pricequote is issued to a customer 110, a copy may also be provided to theidentified dealer 120.

FIGS. 6 and 7 collectively illustrate a flow diagram of an improveddatabase management method through an example system 600 of the presentdisclosure, which leverages distributed computing agents. The system 600is a component of a larger networked system illustrated in FIGS. 10A-G.The system 600 generally comprises a server 602 comprising aVehicleConfigCloudWeb module 604, a VehicleConfigDetailExtractionQueue606, and FranchiseVehicleQuoteSelection 608, and a database 620. Thesystem 600 also comprises remote client 610 that each includes aVehicleConfigClient 612. In general, the system 600 can compriseadditional or fewer components than those illustrated in FIG. 6.

As illustrated in FIG. 7, in some embodiments the system 600 providesdistributed computing, and specifically querying of dealership inventorythrough distribution of the VehicleConfigClient 612 to each remoteclient 610 (see FIG. 6 for remote clients and system). TheVehicleConfigClient 612 is installed on a remote client 610 such as aninventory computing system of a dealership. Various dealerships across acountry or the world can interconnect with the server 602 throughinstallation of the VehicleConfigClient 612.

In some embodiments, the remote client 610 can cooperate with OEM(original equipment manufacturer) systems 611.

The VehicleConfigCloudWeb 612 acts as a mediator or director for allremote inventory operations conducted by the VehicleConfigClient 612installed remotely. In some embodiments, queries for specific inventoryare distributed to one or more of the remote clients based on a querytype. For example, if the query is for a specific manufacturer vehicletype, the query is tailored to the specific requirements or attributesused by the manufacturer to describe their vehicle models. Othernon-manufacturer specific query limitations can also be included such asprice, miles, and so forth. In some embodiments, these portions of thequery that include non-manufacturer specific information can be used inan initial query executed by the remote client 610 that locates thinlocator style records.

In general, when a remote client is operating on a large inventory thetime required to execute a single query and obtain information may betoo great. Query distribution helps remote clients obtain requested datain parallel without causing delays.

In some embodiments, remote clients 610 perform a full collection of allvehicle inventory entries visible to them. This may cause significantload on not only the remote clients and the OEM original equipmentmanufacturer system being targeted for collection, but also any localsystems extracting and processing these vehicle inventory entries.Furthermore, this load may cause significant delays throughout thevarious stages of the process (see full flow in FIGS. 10A-G). Vehicleinventory may become “stale” (weeks or even months out of date),resulting in customer complaints due to processing delays in generatingquery responses.

It will be understood that at least a portion of the remote clients haveoverlapping vehicle inventory views. For example, several dealershipsmay sell vehicles that have similar attributes to one another.Significant computing resources may be expended on duplicated entries orinefficient scheduling.

In some embodiments, the VehicleConfigCloudWeb 604 and client sideVehicleConfigClient 612 are enhanced to operate as an intelligentnetwork of client nodes that are context aware. VehicleConfigClients arenow directed to perform specific extraction operations relative tocurrent vehicle inventory queries. These queries can cover attributessuch as status, specific OEM, year, make, model, and trim—just to name afew. This information can be obtained, for example, from OEM or dealerinventory systems.

These coordinated, context-aware methods of inventory collection allowsfor significant enhancements to the processing and importing of incominginventory data from remote clients 610. Vehicle inventory data can nowbe processed incrementally and differentially.

These process improvements, such as using distributed agents and thinlocator style records, have allowed for maintaining an operating set ofvehicle inventory records that are never more than 24 hours out of date.These improvements have also made VehicleConfigClient 612 lessdisruptive to remote client 610 and OEM systems and networks.

Historically, vehicle inventory data is imported into and consumed froma RDBMS (relational database management system) in a standard “thick”relational data model. Performance and scalability issues becamesignificant obstacles when attempting to leverage vehicle inventorydata. The VehicleConfigDetailExtractionQueue 606 can become backloggedresulting in delays in processing incoming inventory updates of days ormore.

The present disclosure provides an improved method that leverages aNoSQL data-tier of semi-structured data that represents an entirevehicle inventory record with all associated metadata. This embodimentprovides efficiencies as placing the database into a NoSQL data-tierincrease data availability. The VehicleConfigDetailExtractionQueue 606executes an improved RDBMS schema to provide thin locator style recordsthat remain resident in memory, such as a cache memory 622 of the system600. Consumers of this data can now quickly locate vehicle inventory byusing key identifiers (VIN, year, make, model, MSRP, region, and so on)and access the full vehicle inventory record with a subsequent call to adistributed NoSQL system.

As mentioned above, remote agents are located in specific geographicallocations associated with dealerships that comprise inventory. If aprior query for a vehicle in a geographical location has been resolvedby one or more remote agents the server will use a solution generated bythe one or more remote agents rather than refreshing a response to thequery.

Thus, the VehicleConfigDetailExtractionQueue 606 is configured toperform a preliminary query for high level database field information(e.g., data included in thin locator style records), which is followedby a subsequent call for full records when one or more responses fromthe initial query are selected for further review. In some embodiments,an endpoint of the distributed inventory system is a quoting engine,represented by FranchiseVehicleQuoteSelection 608.

These enhancements allow the system 600 to deliver much more granularinventory selections to customers in a significantly reduced time. Thesystem 600 is not bound to specific algorithms such as median MSRP whenselecting alternatives and can now make intelligent selections based oncontextual elements present in a lead such as vehicle year, make, model,and body style—just to name a few.

Also, as mentioned above, the remote agents are distributed and residein various specific geographical locations. If a query has been recentlyresolved in the same local geographical area by remote agents, theserver may not attempt to refresh that query, but will use the priorresults.

Peak quote generation times using the system 600 have been reduced by anorder of magnitude, from sometimes exceeding an hour to often processedand generated in less than three minutes.

Advantageously, the system 600 provides improvements in specificmetrics. For example, mean vehicle inventory freshness metric has beenimproved from one to seven days to less than 24 hours. Peak mean quitedelay metric would improve from 60 minutes to approximately threeminutes. System vehicle inventory capacity improves from 100,000 entriesto an infinite number of horizontal entries. Available alternativeselection parameters have been expanded from the system 600 only usingmanufacturer suggested retail price to using any permutation of anynumber of parameters. In some embodiments, a vehicle blob comprises data(e.g., attributes) of a single vehicle whereas a franchise blob caninclude a franchise inventory list of vehicles and their attributes.

FIG. 8 is a schematic diagram of another example cloud-basedimplementation of the distributed computing systems of the presentdisclosure. The system 800 of FIG. 8 comprises a specific cloud-basedembodiment of the system disclosed above with respect to FIGS. 6 and 7.In one embodiment, the system 800 comprises a cloud computingenvironment 802, a plurality of web clients (e.g., end users) 804, andan inventory database 806.

In some embodiments, an inventory import process 808 provides near-realtime inventory information from remote agents associated with the remoteclients that install the remote agents (see FIGS. 6 and 7 as anexample). The inventory information can comprise any of thin recordsand/or complete or full records. Inventory can also be received from aRVS inventory process 810 (e.g., remote client 610 andVehicleConfigClient 612). Additionally, the inventory information canoriginate from a non-dealership source 811. The non-dealership sourcecan include but is not limited to salvage companies, leasing companies,and auto rental agencies or any other company that sells vehicles. Thenon-dealership source can be configured with a remote agent and caninclude an interface 811 a to support communications between thenon-dealership companies 811 and the database 806.

The inventory database 806 provides inventory blobs (comprises vehicleinformation in some embodiments) in an export process 812 to the cloudcomputing environment 802. These blobs are imported into the cloudcomputing environment 802 as records, such as inventory data records814.

In some embodiments, the cloud computing environment 802 comprises webservers such as web server 816 that processes queries received from theplurality of web clients 804 and returns results to the plurality of webclients 804.

FIG. 9 is a flow diagram of an example method of the present disclosure.The method includes a step 902 of distributing remote agents to aplurality of remote computing systems. Again, the remote agents can beinstalled on the computing systems of dealerships in varied geographicallocations. In some embodiments, the method includes a step 904 ofreceiving incoming inventory from the database of available inventoryvia the remote agents. In some embodiments, the remote agents canschedule transmissions of inventory records to a cloud service such thatthe cloud service has a continually updated inventory database availablefor querying against. Additionally, the method can include a step 905 ofgenerating standardized inventory records received via the remoteagents. The generating standardized inventory records 905 can includetokenizing each field of the received record associated with thedatabase and converting all or some of the fields into a standardizedrecord format. This step 905 operates as described above where a fieldssuch as the vehicle make, “CHEVY”, is converted to the standard recordformat “CHEVROLET.” This standardization conversion can occur for someor all of the fields in the inventory record. These fields can includebut are not limited to vehicle year, make, model, and body style. Aperson skilled in the art of database programming would be able totokenize an inventory string, convert the fields into a standard formbefore loading the standardized inventory record into the database.

According to some embodiments, the method comprises a step 906 ofgenerating a database of available inventory that comprises completeinventory records. Again, this can include thin or full inventoryrecords as described above.

The method also comprises a step 908 of generating thin locator stylerecords for the complete inventory records. The thin locator stylerecords comprise key record identifiers that are indicative of thecontent included in the complete record. For example, key recordidentifiers could include VIN, year, make, model, MSRP, region, and soon. When a query is executed it can include a permutation of these keyrecord identifiers, which allows the cloud service to pare results fromthe full inventory.

Next, the method includes a step 910 a query is received. In a step 911,the query is converted to a standardized query. The fields in the queryare converted to a form that match the fields in the database andthereby enabling a database search based on standard terms. In otherembodiments, the query can be executed against an inventory databaseavailable to the cloud service. According to some embodiments the querycan comprise a price matching quote as described in greater detail withrespect to the embodiments of FIGS. 1A-5C.

In some embodiments, the method comprises a step 912 of selecting thinlocator style records in response to the query. Again, this step cancomprises using key record identifiers included in a price matchingquote to cull or select from the thin locator style records thatcorrespond to the key record identifiers. In some embodiments, the cloudservices allows for exact or fuzzy matching where records that includesome but not all of the key record identifiers in the price matchingquote are selected.

According to some embodiments, the method comprises a step 914 ofobtaining complete inventory records corresponding to the thin locatorstyle records of the selected key record identifiers. For example, auser can select one or more of the inventory records based on theretrieval of thin locator style records. The cloud service can thenobtain the full inventory records based on the selection(s).

In some embodiments, the method comprises a step 916 of providing thecomplete inventory records to a requestor. For example, this couldinclude displaying the records on a display device, emailing therecords, or other similar methods of delivery of a database record.

Collectively, FIGS. 10A-G illustrate a price quote matching methodologythat integrates the distributed computing and database improvementsdescribed above. To be sure, FIG. 10F corresponds to FIG. 7 which wasdescribed in greater detail supra.

Some of the above-described functions can be composed of instructionsthat are stored on storage media (e.g., computer-readable medium). Theinstructions may be retrieved and executed by the processor. Someexamples of storage media are memory devices, tapes, disks, integratedcircuits, and servers. The instructions are operational when executed bythe processor to direct the processor to operate in accord with theinvention. Those skilled in the art are familiar with instructions,processor(s), and storage media.

It is noteworthy that any hardware platform suitable for performing theprocessing described herein is suitable for use with the invention. Theterms “computer-readable medium” and “computer-readable media” as usedherein refer to any medium or media that participate in providinginstructions to a CPU for execution. Such media can take many forms,including, but not limited to, non-volatile media, volatile media andtransmission media. Non-volatile media include, for example, optical ormagnetic disks, such as a fixed disk. Volatile media include dynamicmemory, such as system RAM. Transmission media include coaxial cables,copper wire and fiber optics, among others, including the wires thatcomprise one embodiment of a bus. Transmission media can also take theform of acoustic or light waves, such as those generated during radiofrequency (RF) and infrared (IR) data communications. Common forms ofcomputer-readable media include, for example, a floppy disk, a flexibledisk, a hard disk, magnetic tape, any other magnetic medium, a CD-ROMdisk, digital video disk (DVD), any other optical medium, punch cards,paper tape, any other physical medium with patterns of marks or holes, aRAM, a PROM, an EPROM, an EEPROM, a FLASHEPROM, any other memory chip orcartridge, a carrier wave, or any other medium from which a computer canread.

Various forms of computer-readable media may be involved in carrying oneor more sequences of one or more instructions to a CPU for execution. Abus carries the data to system RAM, from which a CPU retrieves andexecutes the instructions. The instructions received by system RAM canoptionally be stored on a fixed disk either before or after execution bya CPU.

The above description is illustrative and not restrictive. Manyvariations of the invention will become apparent to those of skill inthe art upon review of this disclosure. The scope of the inventionshould, therefore, be determined not with reference to the abovedescription, but instead should be determined with reference to theappended claims along with their full scope of equivalents.

While the present invention has been described in connection with aseries of preferred embodiment, these descriptions are not intended tolimit the scope of the invention to the particular forms set forthherein. It will be further understood that the methods of the inventionare not necessarily limited to the discrete steps or the order of thesteps described. To the contrary, the present descriptions are intendedto cover such alternatives, modifications, and equivalents as may beincluded within the spirit and scope of the invention as defined by theappended claims and otherwise appreciated by one of ordinary skill inthe art.

What is claimed is:
 1. A method, comprising: distributing remote agentsto a plurality of remote computing systems; receiving incoming inventoryfrom a database of available inventory via the remote agents; generatingstandardized inventory records received via the remote agents;generating the database of available inventory that comprises completestandardized inventory records; generating thin locator style recordsfor the complete standardized inventory records, wherein the thinlocator style records comprise key record identifiers; receiving aquery; generating a standardized query; selecting the thin locator stylerecords in response to the standardized query; obtaining the completestandardized inventory records corresponding to the thin locator stylerecords of the selected key record identifiers; and providing thecomplete inventory records to a requestor.
 2. The method according toclaim 1, wherein each of the plurality of remote computing systems iscoupled with an original equipment manufacturer system and at least aportion of the complete inventory records are obtained from the originalequipment manufacturer system.
 3. The method according to claim 1,wherein each of the plurality of remote computing systems is coupledwith an non-dealership system and at least a portion of the completeinventory records are obtained from the non-dealership system.
 4. Themethod according to claim 1, wherein the incoming inventory is receivedperiodically from the remote agents.
 5. The method according to claim 1,wherein the database stores information concerning a plurality ofvehicles available for sale, the stored information including aplurality of features for each vehicle.
 6. The method according to claim5, wherein the standardized query comprises a price quote request, theprice quote request specifying a make and model for a requested vehicle.7. The method according to claim 6, wherein the complete standardizedinventory records comprise a first set of vehicles from the plurality ofvehicles which match the make and model of the requested vehicle.
 8. Themethod according to claim 7, further comprising determining that a firstset of complete standardized inventory records does not meet apredefined target, the predefined target including a minimum number ofvehicles for inclusion in the price quote response; identifying a bodystyle of the requested vehicle; and retrieving a second set of completestandardized inventory records from the database, the second set ofcomplete inventory records including a second set of vehicles from theplurality of vehicles which match at least the body style of therequested vehicle.
 9. The method according to claim 8, furthercomprising: selecting a third set of vehicles from the first and secondsets of complete inventory records for the price quote response inaccordance with the predefined target; and generating the price quoteresponse.
 10. The method of claim 1, wherein the minimum number ofvehicles is defined prior to receiving the price quote request.
 11. Themethod of claim 1, wherein the incoming inventory is received and thinlocator style records are generated such that the database of availableinventory never more than 24 hours old.
 12. A system, the systemcomprising: remote agents distributed to a plurality of remote computingsystems; and a server in communication with the remote agents that:receives incoming inventory from a database of available inventory fromthe remote agents; generates a standardized inventory record; generatesthe database of available inventory that comprises complete standardizedinventory records; generates thin locator style records for the completestandardized inventory records, wherein the thin locator style recordscomprise key record identifiers; receives a query; generates astandardized query; selects the thin locator style records in responseto the standardized query; obtains the complete standardized inventoryrecords corresponding to the thin locator style records of the selectedkey record identifiers; and provides the complete standardized inventoryrecords to a requestor.
 13. The system according to claim 12, whereineach of the plurality of remote computing systems is coupled with anoriginal equipment manufacturer system and at least a portion of thecomplete inventory records are obtained from the original equipmentmanufacturer system.
 14. The system according to claim 12, wherein eachof the plurality of remote computing systems is coupled with annon-dealership system and at least a portion of the complete inventoryrecords are obtained from the non-dealership system.
 15. The systemaccording to claim 12, wherein the incoming inventory is receivedperiodically from the remote agents in an incremental manner.
 16. Thesystem according to claim 12, wherein the database stores informationconcerning a plurality of vehicles available for sale, the storedinformation including a plurality of features for each vehicle.
 17. Thesystem according to claim 16, further comprising: determining that afirst set of complete standardized inventory records does not meet apredefined target, the predefined target including a minimum number ofvehicles for inclusion in the price quote response; identifying a bodystyle of the requested vehicle; retrieving a second set of completeinventory records from the database, the second set of completeinventory records including a second set of vehicles from the pluralityof vehicles which match at least the body style of the requestedvehicle; selecting a third set of vehicles from the first and secondsets of complete inventory records for the price quote response inaccordance with the predefined target; and generating the price quoteresponse.
 18. The system according to claim 17, wherein the querycomprises a price quote request, the price quote request specifying amake and model for the requested vehicle, and further wherein thecomplete inventory records comprise a first set of vehicles from theplurality of vehicles which match the make and model of the requestedvehicle.
 19. The system according to claim 18, wherein the remote agentsare located in specific geographical locations, further wherein if aprior query for another vehicle in a geographical location has beenresolved by one or more remote agents, the server will use a solutiongenerated by the one or more remote agents rather than refreshing aresponse to the query.